|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3436 (2002)
|
|
Title:
|
Transport Layer Security over Stream Control Transmission Protocol
|
|
|
2.
|
Status of approval:
|
|
|
Standards track - Proposed Standard (December 2002)
|
|
3.
|
Justification for the specific reference:
|
|
|
H.248.91 defines requirements and profile guidelines for TLS bearer traffic, which includes the TLS transport mode "TLS-over-SCTP".
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3436
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards Track RFC
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2246] Diercks, T. and C. Allen, "The TLS Protocol Version/
1.0", RFC 2246, January 1999./
/
[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C.,/
Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M.,/
Zhang, L. and V. Paxon, "Stream Control Transmission/
Protocol", RFC 2960, October 2000./
/
[RFC3268] Chown, P., "Advanced Encryption Standard (AES)/
Ciphersuites for Transport Layer Security (TLS)", RFC/
3268, June 2002./
/
[RFC3309] Stone, J., Stewart, R., Otis, D., "Stream Control/
Transmission Protocol (SCTP) Checksum Change", RFC 3309,/
September 2002./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
none
|
|
